Repository navigation
chore(deps): bump changesets/action from 1.9.0 to 2.1.2 - #11
Merged
Merged
Conversation
Bumps [changesets/action](https://github.com/changesets/action) from 1.9.0 to 2.1.2. - [Release notes](https://github.com/changesets/action/releases) - [Changelog](https://github.com/changesets/action/blob/main/CHANGELOG.md) - [Commits](changesets/action@a45c4d5...ae32849) --- updated-dependencies: - dependency-name: changesets/action dependency-version: 2.1.2 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
e110c0
approved these changes
Nov 10, 2026
e110c0
added a commit
that referenced
this pull request
Nov 11, 2026
## Summary The Release workflow has failed on every push to `main` since Dependabot bumped `changesets/action` from v1.9.0 to v2.1.2 (#11). v2 renamed four inputs, and the workflow still passed the old names: ``` Warning: Unexpected input(s) 'version', 'publish', 'title', 'commit', valid inputs are ['github-token', 'publish-script', 'version-script', 'commit-message', 'pr-title', ...] Error: The following inputs have been renamed: ... ``` ## Change `.github/workflows/release.yml` only, same values with the new names: | Before | After | |---|---| | `version` | `version-script` | | `publish` | `publish-script` | | `title` | `pr-title` | | `commit` | `commit-message` | Names checked against the v2.1.2 `action.yml`. The npm authentication (trusted publishing through OIDC, with the unused `NPM_TOKEN` env left as is) is unchanged on purpose, so the setup that published 8.0.0 is untouched. ## Notes - All four packages are already published at 8.0.0, so nothing was lost; the Release job just never reached the publish step. - In v2, `push-git-tags` and `create-github-releases` default to `true`. Future releases get git tags and GitHub releases; the 8.0.0 release is not backfilled. - After merging, the next Release run on `main` should find no changesets and nothing unpublished, and finish green. This is the first run on v2, so any further error would show up there. Co-authored-by: Dirk Haage <dirk@mohawk.pro> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps changesets/action from 1.9.0 to 2.1.2.
Release notes
Sourced from changesets/action's releases.
... (truncated)
Changelog
Sourced from changesets/action's changelog.
... (truncated)
Commits
ae32849v2.1.20138f45Version Packages (#726)8833883Handle error when pushing git tags with the git CLI (#735)e08fde7Improve log messages (#730)371fd77Bump human-id in the production-dependencies group across 1 directory (#732)85efcafBump actions/checkout in the github-actions group across 1 directory (#734)5bb9d5cBump the development-dependencies group across 1 directory with 7 updates (#733)ca85897Always prepare branch for version (#729)36f529fFix root action double error logs (#724)d7669c8Version Packages (#722)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)